Proposed changes

Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.

If this relates to a card, please include a link to the card here. Additionally, please terminate the PR title with # and the card number, such as Fix doomsday bug #1234

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix: non-breaking change which fixes an issue)
• New feature: non-breaking change which adds functionality)
• Chore: changes to the build process, continuous integration (CI) tools, or auxiliary tools and libraries
• Test: adding or modifying tests
• Docs: documentation changes
• Perf: a code change that improves performance
• Style: changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• Refactor: a code change that neither fixes a bug nor adds a feature

Please indicate if your PR introduces a breaking change

• Breaking change: fix or feature that would cause existing functionality to not work as expected

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the Contributing doc
• I have read the Git and PR best practices at LinkORB guide doc
• Lint and unit tests pass locally with my changes
• I have added/updated necessary documentation in the README.md or doc/ directories (if appropriate)

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...